-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failover configuration #760
Conversation
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
/** | ||
* RPC API Keys. Used to authenticate users on RPC Server. | ||
*/ | ||
apiKeys: string; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should this be string[]
as well when nodeUrl is string[]
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh I think it's good. The use case is for fallback, should have same apiKey
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Is this PR ready? This allows failover logic with config for multiple RPC providers? |
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
Any updates? |
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
@MaximusHaximus ptal :) |
This PR is stale because it has been open for 7 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
This PR is stale because it has been open for 14 days with no activity. Remove stale label or comment or this will be closed in another 7 days. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
merge
we need fallback also |
Hey @frol, do you want this PR to be merged? If so, we suggest closing the existing PR and moving all the changes to a new one. It will be much easier for us to resolve the conflicts that way. What do you think? |
Sure, makes sense. I would keep this PR open until a new one is submitted, so we don't lose track of it. |
This functionality has been merged with #1334 |
Closing #733
With this design of failover, we will change (rotate) our server when needed and stick to this new server for our next calls. It will help to avoid long responses when first (or more) servers are down.
For now, server rotation is happening only on
Timeout
error.Also, check this comment: #733 (comment)